Exclude 7FFFh from DPT9 ParamType as Used for "Invalid Data" and Ignored by Stack #92
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cornelius-koepp
added
bug
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Der Stack schreibt für DPT9 keine Werte >670433, da der nächstgrößere Wert 670760~=0x7FFF reserviert ist zur Codierung von ungültigen Werten.
Die Änderung von ParameterType
%AID%_PT-ValueDpt9hat Einfluss auf bestehende Module, die Parameter dieses Typs einsetzen. Siehe https://github.com/search?q=org%3AOpenKNX%20PT-ValueDpt9&type=code (durchsucht nur Default-Branch). Mindestens folgende:Ggf. ist es daher besser, wenn wir diesen Typ ersetzten durch einen anders benannten